CAC Sales Website — Owner's Manual

Everything you need to maintain, update, and deploy this site.

PART 1: THE MAP

What exists and where

SalesWebsite/
├── index.html              ← Home / Programme page
├── about/index.html        ← About Lovinia
├── pricing/index.html      ← Pricing table + flipbook ← NEW
├── faq/index.html          ← FAQ ← NEW
├── register/index.html     ← Registration + Stripe ← NEW
├── _data/trainer.json      ← Shared trainer data ← NEW
├── articles/               ← Articles (existing)
├── privacy-policy.html     ← Existing
├── assets/                 ← Images and static files
└── _site/                  ← Auto-generated. DO NOT EDIT.

Rule: Never edit anything inside _site/. It is overwritten every build.

PART 2: THE ONE THING YOU NEED TO KNOW

Every page has a CONFIG block at the top of the <script> section. It is clearly marked:

<!-- CONFIG BLOCK — EDIT THIS SECTION ONLY -->

You never need to touch the HTML below it. All updates go in the CONFIG block.

PART 3: HOW TO UPDATE THINGS

A. Change the event date

Open pricing/index.html and register/index.html. Find:

date: "May 5–6, 2025",
earlybird_deadline: "2025-04-05",

Change both values. The early bird countdown and pricing auto-update from these two fields.

Format for earlybird_deadline: Always YYYY-MM-DD. The system calculates 30 days automatically — you set the exact cutoff date, not "30 days before."

B. Add course schedule content (Day 1 & Day 2)

Open pricing/index.html. Find the schedule block in CONFIG:

schedule: {
  day1: {
    title: "Day One",
    subtitle: "Foundation & Framework",
    sessions: [
      { time:"9:00 – 10:30am", topic:"[ADD: Session title]", detail:"[ADD: description]" },
      { time:"10:30 – 10:45am", topic:"Morning Break", break:true },
      ...
    ]
  }
}

Replace the [ADD: ...] placeholders. Do not change the time values — those are fixed. Only change topic and detail.

For breaks: Keep break:true and only change the topic text if needed. Do not add detail to break rows.

C. Add real testimonials

Open pricing/index.html. Find:

testimonials: [
  { placeholder:true, quote:"", name:"", role:"" },
  ...
],

Replace with:

{ placeholder:false, quote:"The actual quote from the participant.", name:"First Last", role:"Job Title, Company" },

Set placeholder:false and fill in all three fields. The placeholder card disappears automatically.

D. Update trainer bio

Open _data/trainer.json. Edit the paragraphs array. This is the single source of truth — currently only used by the flipbook page. In a future session, we can wire about/index.html to read from this file too, replacing its SITE_CONFIG.

E. Add an announcement

Open pricing/index.html. Find:

announcements: [
  "Existing announcement here.",
],

Add a new line inside the array. Use <strong>text</strong> for bold. To remove an announcement, delete its line. To hide all announcements, set the array to [].

F. Add Stripe payment links

Open register/index.html. Find the stripe: block in CONFIG. Replace each "REPLACE_WITH_..." placeholder with the actual Stripe Payment Link URL.

You will have 12 links in total: 3 ticket types × 2 payment methods (card + FPX) × 2 pricing tiers (early bird + standard).

How to get Stripe Payment Links:

1. Log in to stripe.com → Products → Payment Links
2. Create a link for each price point
3. For FPX: in Payment Link settings, under Payment Methods, enable FPX (Malaysian banks)
4. Copy the URL (starts with https://buy.stripe.com/...)
5. Paste into CONFIG

PART 4: HOW TO BUILD AND DEPLOY

First time setup (one-time)

cd ~/Documents/github/SalesWebsite
npm install

Preview locally

cd ~/Documents/github/SalesWebsite
npx eleventy --serve

Opens at http://localhost:8080. Saves automatically on file changes.

Deploy to Cloudflare

cd ~/Documents/github/SalesWebsite
npx eleventy && wrangler deploy

This builds the _site/ folder then pushes to Cloudflare Workers.

Push to GitHub (version control)

cd ~/Documents/github/SalesWebsite
git add -A
git commit -m "describe what you changed"
git push

Do this after every change. Habit, not optional.

PART 5: COPYING THE NEW FILES INTO YOUR PROJECT

Run these commands once to add the new pages:

# Copy new pages
cp -r ~/Desktop/SalesWebsite-build/pricing ~/Documents/github/SalesWebsite/
cp -r ~/Desktop/SalesWebsite-build/faq ~/Documents/github/SalesWebsite/
cp -r ~/Desktop/SalesWebsite-build/register ~/Documents/github/SalesWebsite/
cp -r ~/Desktop/SalesWebsite-build/_data ~/Documents/github/SalesWebsite/

# Fix the broken pricing link in index.html
sed -i '' 's|PRICING-PAGE-LINK-HERE|/pricing/|g' ~/Documents/github/SalesWebsite/index.html

Then verify Eleventy sees the new folders:

cd ~/Documents/github/SalesWebsite && npx eleventy --dryrun 2>&1 | grep -E "pricing|faq|register"

You should see three lines — one for each new page.

PART 6: CLOUDFLARE — WHAT IT IS AND WHAT YOU HAVE

What Cloudflare Workers is

Your site is hosted on Cloudflare Workers — not a traditional web server. Think of it as a very fast delivery network that runs your site from data centres closest to each visitor. Zero monthly cost on the free tier.

What you get free

• 100,000 requests per day
• Workers KV storage: 100,000 reads/day, 1,000 writes/day, 1GB storage
• Custom domain support
• Automatic HTTPS

This is more than enough for your current scale.

Setting up lead capture (Cloudflare Workers KV)

This is for the "Notify Me" form on the pricing page and the in-house enquiry form on the register page. Both currently send a POST request to https://YOUR-WORKER.workers.dev/.... You need to create a Worker to receive and store these.

Step-by-step:

1. Log in to dash.cloudflare.com
2. Go to Workers & Pages → Create Application → Create Worker
3. Name it cac-leads
4. Paste this code into the editor:

export default {
  async fetch(request, env) {
    if (request.method === 'OPTIONS') {
      return new Response(null, {
        headers: {
          'Access-Control-Allow-Origin': '*',
          'Access-Control-Allow-Methods': 'POST',
          'Access-Control-Allow-Headers': 'Content-Type',
        }
      });
    }
    if (request.method !== 'POST') {
      return new Response('Not found', { status: 404 });
    }
    const url = new URL(request.url);
    const body = await request.json();
    const key = `${url.pathname.replace('/','')}_${Date.now()}_${Math.random().toString(36).slice(2,7)}`;
    await env.LEADS.put(key, JSON.stringify(body));
    return new Response(JSON.stringify({ ok: true }), {
      headers: {
        'Content-Type': 'application/json',
        'Access-Control-Allow-Origin': '*',
      }
    });
  }
};

5. Go to Settings → Bindings → KV Namespace Bindings
6. Add binding: variable name LEADS, create a new namespace called cac-leads-kv
7. Deploy
8. Copy your worker URL (e.g. https://cac-leads.YOUR-SUBDOMAIN.workers.dev)
9. In pricing/index.html and register/index.html, replace https://YOUR-WORKER.workers.dev with your actual worker URL

To read your leads:

wrangler kv:key list --namespace-id YOUR_KV_NAMESPACE_ID
wrangler kv:key get --namespace-id YOUR_KV_NAMESPACE_ID "key_name_here"

Or export all:

wrangler kv:key list --namespace-id YOUR_KV_NAMESPACE_ID > leads_keys.txt

Get your namespace ID from the Cloudflare dashboard → Workers & Pages → KV.

PART 7: YOUR TO-DO LIST (IN ORDER)

Before launch

• [ ] Copy new files into project (commands in Part 5)
• [ ] Fix pricing link in index.html (command in Part 5)
• [ ] Run npx eleventy --serve and check all three new pages load
• [ ] Set up Cloudflare Worker for lead capture (Part 6)
• [ ] Create Stripe Payment Links (12 total — see Part 3F)
• [ ] Drop Stripe links into register/index.html CONFIG

When you have schedule content

• [ ] Add Day 1 session topics to pricing/index.html CONFIG
• [ ] Add Day 2 session topics to pricing/index.html CONFIG

When you have testimonials

• [ ] Replace placeholder testimonial objects in pricing/index.html CONFIG

When date changes

• [ ] Update date and earlybird_deadline in BOTH pricing/index.html and register/index.html
• [ ] Update Stripe Payment Links if pricing changes

Ongoing

• [ ] After every edit: git add -A && git commit -m "what changed" && git push
• [ ] After every deploy: npx eleventy && wrangler deploy

PART 8: LINKS BETWEEN PAGES — THE FULL MAP

PART 9: WHAT NOT TO TOUCH

• _site/ — auto-generated, always overwritten
• node_modules/ — dependency folder, never edit
• The HTML below each CONFIG block — structure only, no content lives there
• package-lock.json — auto-managed

PART 10: IF SOMETHING BREAKS

Page not showing after deploy:

npx eleventy --dryrun

Look for errors. Usually a missing file or malformed path.

Eleventy build fails:

npx eleventy 2>&1 | head -40

Read the first error. Usually a Liquid/Nunjucks syntax error in a template.

Wrangler deploy fails:

wrangler whoami

If not logged in: wrangler login

Local preview not updating: Stop the server (Ctrl+C), clear _site/:

rm -rf _site && npx eleventy --serve

End of manual. Version 1.0 — April 2026.

Session Log: cac-corporate-enquiry Debug (2026-04-26)

What was broken

Enquiry form at sales-training/enquiry stopped working after CRM was built.

Root causes found (in order)

1. Wrong worker URL — form posted to cac-leads.../corporate-enquiry (lead capture worker). Should be cac-corporate-enquiry.clarityawarenesscoaching.workers.dev. Fixed in sales-training/enquiry/index.html.
2. D1 binding named wrong — Cloudflare dashboard had binding named D1 instead of DB. Worker code uses env.DB. Fixed manually on dashboard (rename binding to DB).
3. Wrong table — Worker was rewritten for CRM and tried to upsert into contacts table. Live contacts is a B2B company master (company_name, general_email, pic_name — not a person/lead table). Enquiry data belongs in enquiries table. Fixed in src/index.js.
4. Wrong interactions columns — Worker used outcome and initiated_by which don't exist in live interactions table. Live schema has worker_event instead. Fixed.
5. FK constraint on interactions — interactions.contact_id has a foreign key on contacts(id). Enquiry row id is not a contacts id. Removed interactions insert entirely — enquiries table is the log for this worker.

Files changed

• sales-training/enquiry/index.html — worker URL fix
• workers/cac-corporate-enquiry/src/index.js — DB writes corrected

Live schema reference (claritysystems-db)

• enquiries — id INTEGER PK (autoincrement), name, email, phone, company, company_address, course, pax, tentative_date, venue, hrdc_option, message, status, created_at
• interactions — id INTEGER PK, contact_id INTEGER (FK → contacts.id), direction, channel, summary, worker_event, resend_email_id, created_at
• email_events — id TEXT PK, contact_id TEXT (no FK), campaign_id, sequence_step, resend_email_id, event_type, event_time, metadata
• contacts — id INTEGER PK, company_name, general_email, phone, pic_name, hr_name, hr_email, linkedin_url, source, outreach_status, preferred_training, campaign_id, assigned_course, created_at, updated_at, tax_metadata

Next Build: New Rise Training Provider Enquiry Flow

What it is

Replicate the sales-training/enquiry workflow for the Training Provider (New Rise or equivalent). Subdomain: newrise.claritysystems.work/enquiry (or similar).

What changes from CAC flow

Confirmed requirements

1. Enquiry form — TP branding replacing CAC brand
2. Duplicate worker newrise-corporate-enquiry — TP details in proforma, payment, issued-by blocks
3. Attachments — trainer profile, proforma invoice, tentative course schedule (TP billing details)
4. Separate data store — new D1 database or Google Sheet for TP enquiries (decision pending)
5. Confirmation flow — when client replies to confirm, send true invoice + confirmed schedule + trainer profile

Open decisions before build

• TP company name, address, bank details, contact email
• TP logo URL (R2 or external)
• Separate D1 database vs new table in claritysystems-db vs Google Sheet
• Email sending domain — does TP have a domain or send via CAC?
• Telegram — same chat or separate notification channel
• Subdomain DNS — newrise.claritysystems.work needs a Cloudflare Pages deployment or redirect

What Lovinia needs to prepare

• TP company details (name, address, bank, email)
• TP logo (upload to R2 or provide URL)
• Decision on database (simplest: new table newrise_enquiries in same claritysystems-db, zero new infrastructure)
• Confirmation flow trigger — email reply parsed by worker, or manual step?

Session prompt for next build

Read BUILD_LOG.md and my work notes/OWNERS_MANUAL.md (New Rise section).

Task: Build the New Rise TP enquiry flow.

Stack: Same as CAC — Cloudflare Pages subdomain + new Worker + claritysystems-db (new table newrise_enquiries).

Start with:
1. Duplicate sales-training/enquiry/index.html → newrise/enquiry/index.html with TP branding
2. Duplicate workers/cac-corporate-enquiry → workers/newrise-corporate-enquiry with TP details
3. Add newrise_enquiries table to claritysystems-db
4. Wire subdomain newrise.claritysystems.work on Cloudflare Pages

TP details: [INSERT BEFORE SESSION]